Skip to content

Conversation

brendan-ward
Copy link
Member

Resolves #107

As I understand it, a recent pip upgrade now runs into issues with oldest-supported-numpy declared in pyproject.toml when running with --no-build-isolation when numpy isn't yet installed. The fix is to add --no-use-pep517.

This updates to do the same thing as pandas: pandas-dev/pandas#47015

python3 -m pip install --no-cache-dir -U pip wheel
python3 -m pip install --no-cache-dir cython~=0.29
python3 -m pip install --no-cache-dir --no-build-isolation -e .[dev,test,geopandas]
python3 -m pip install --no-cache-dir --no-build-isolation --no-use-pep517 -e .[dev,test,geopandas]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, we could also remove the --no-build-isolation altogether and test the default pip installation in this workflow (and then we can also remove the cython install step on the line above)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's cleaner.

@brendan-ward brendan-ward merged commit 23889ae into main May 16, 2022
@brendan-ward brendan-ward deleted the fix_pip_oldest_numpy branch May 16, 2022 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI: Docker-based tests failing due to oldest-supported-numpy

2 participants